X3 session logs

A user-friendly tool for runtime logs

Enhancing the ability of Sage X3 consultants and administrators to troubleshoot Sage X3 solutions and to analyze architecture issues is a priority.

This document describes a new Sage X3 administration feature delivered in release 2021 R3/V12.0.27. This function allows Sage X3 administrators to enable runtime logging easily, with a few clicks, session-wide, or with a more focused target.

Administrators can now:

• Define log settings with names and references

• Enable or disable logging from the menu

• Select the necessary log levels and log details through a user-friendly interface

• Define filtering criteria to focus on desired users or areas if needed

Sage X3 session

A Sage X3 session (or runtime session) is started whenever a user logs into a Sage X3 classic function for the first time after logging into the Sage X3 homepage. It is then stored as a reuse session on the home page whenever the user exits for him to reuse it in the future.

There can be as many Sage X3 session instances as browser instances or tabs using a Sage X3 function (on the same device or different devices), even if they belong to the same Sage X3 user.

Session logs

Session logs are logs written by the Sage X3 runtime to trace application execution logic within a Sage X3 session.

The Sage X3 runtime generates a single log file per session ID (PID process). Log files are stored in the Runtime\logs directory in the Sage X3 runtime installation path for the runtime that manages the session being logged. You can store log files spanning different sessions on multi-runtime instances in different folders on your application servers.